Change llvmcall docs binding
#16332
Merged
Change llvmcall docs binding
#16332
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
AppVeyor failure in abstractarray looks new, probably the fault of #16251 cc @mbauman https://ci.appveyor.com/project/JuliaLang/julia/build/1.0.1501/job/ia6bwd91kg621ii3 |
|
Fix is very straightforward: acafa9b; caused by concurrent changes to |
|
Thanks much. I'll have to make barosl/homu#87 a project. |
The docstring for `llvmcall` was bound to a keyword rather than
the actual intrinsic `Core.Intrinsics.llvmcall`.
This produced the following odd behaviour when trying to find the docs:
help?> llvmcall
... docs ...
julia> llvmcall
ERROR: UndefVarError: llvmcall not defined
help?> Base.llvmcall
... no docs ...
julia> Base.llvmcall
(intrinsic function JuliaLang#90)
MichaelHatherly
force-pushed
the
mh/llvmcall-doc
branch
from
659a04c to
83444aa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The docstring for
llvmcallwas bound to a keyword rather than the actual intrinsicCore.Intrinsics.llvmcall.This produced the following odd behaviour when trying to find the docs: